Specifying and Checking File System Crash-Consistency Models
نویسندگان
چکیده
منابع مشابه
CrashMonkey: A Framework to Systematically Test File-System Crash Consistency
Modern file systems provide a set of mechanisms to ensure consistent recovery of the file system in the event of a computer crash. However, these mechanisms are complex and hard to implement correctly. Furthermore, these mechanisms are time consuming to test, leading to only a cursory set of crash consistency tests being run on new file systems and any patches submitted to existing file systems...
متن کاملFast Consistency Checking for the Solaris File System
Our Netra NFS group at Sun set out to solve the challenging problem of providing remote Network File System (NFS) service with high performance and availability. An NFS server must guarantee the permanence of changes to the file system before acknowledging an NFS request. Thus, the server’s underlying local file system must perform update operations synchronously to stable storage with potentia...
متن کاملSpecifying a Realistic File System
We present the most interesting elements of the correctness specification of BilbyFs, a performant Linux flash file system. The BilbyFs specification supports asynchronous writes, a feature that has been overlooked by several file system verification projects, and has been used to verify the correctness of BilbyFs’s fsync() C implementation. It makes use of nondeterminism to be concise and is s...
متن کاملOn Efficiently Specifying Models for Model Checking
Using formal methods for quality assurance is recommended in many standards for safety critical applications. In most industrial contexts, model checking is the only viable option for formal verification, as interactive approaches often require very highly specialized experts. However, model checking typically suffers from the well-known statespace explosion problem. Due to this problem, engine...
متن کاملIs Ordering of Disk Updates Required to Maintain File-System Crash-Consistency?
On reboot after a crash, the file system should be consistent: e.g., previously correct files should not now contain garbage. In early file systems, getting to a consistent state involved a full scan after reboot. This was very slow, and impractical for large systems. Modern file systems improve upon this by writing updates to disk in a specific order : e.g, metadata before commit blocks. This ...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
ژورنال
عنوان ژورنال: ACM SIGPLAN Notices
سال: 2016
ISSN: 0362-1340,1558-1160
DOI: 10.1145/2954679.2872406